Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(main): release 10.2.0 #3006

Merged
merged 2 commits into from
Jul 10, 2024

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Apr 3, 2024

🤖 I have created a release beep boop

10.2.0 (2024-07-09)

Features

  • allow VCINSTALLDIR to specify a portable instance (#3036) (d38af2e)
  • gyp: update gyp to v0.18.1 (#3039) (ea99fea)
  • support rebuild and build for cross-compiling Node-API module to wasm on Windows (#2974) (6318d2b)

Core

Doc

  • node-pre-gyp is no longer maintained (#3015) (93186f1)
  • add the way to configuring Python dependency for Windows PowerShell (#2996) (9fd7936)
  • Installation -- Python >= v3.12 requires node-gyp >= v10 (#3010) (a6b48fc)

Miscellaneous


This PR was generated with Release Please. See documentation.

@github-actions github-actions bot force-pushed the release-please--branches--main--components--node-gyp branch 3 times, most recently from 85766a1 to d9034f8 Compare April 11, 2024 15:35
@github-actions github-actions bot force-pushed the release-please--branches--main--components--node-gyp branch 3 times, most recently from 5f28e72 to bfdbec9 Compare April 16, 2024 00:05
@github-actions github-actions bot force-pushed the release-please--branches--main--components--node-gyp branch from bfdbec9 to dcaa1ec Compare April 23, 2024 13:46
@github-actions github-actions bot force-pushed the release-please--branches--main--components--node-gyp branch from dcaa1ec to 7d8c177 Compare May 31, 2024 09:26
@github-actions github-actions bot changed the title chore(main): release 10.1.1 chore(main): release 10.2.0 Jun 12, 2024
@github-actions github-actions bot force-pushed the release-please--branches--main--components--node-gyp branch from 7d8c177 to fbfabde Compare June 12, 2024 09:24
CHANGELOG.md Outdated Show resolved Hide resolved
@github-actions github-actions bot force-pushed the release-please--branches--main--components--node-gyp branch 2 times, most recently from d76be63 to a2f3cab Compare June 28, 2024 14:41
@github-actions github-actions bot force-pushed the release-please--branches--main--components--node-gyp branch from a2f3cab to 9672d9d Compare July 9, 2024 15:14
@github-actions github-actions bot force-pushed the release-please--branches--main--components--node-gyp branch from 9672d9d to b4a469c Compare July 9, 2024 17:03
@legendecas
Copy link
Member

This has been open for a couple of months. I can land this tomorrow.

Co-authored-by: Christian Clauss <[email protected]>
@legendecas legendecas merged commit 08c91d0 into main Jul 10, 2024
36 checks passed
@legendecas legendecas deleted the release-please--branches--main--components--node-gyp branch July 10, 2024 12:05
Copy link
Contributor Author

🤖 Release is at https://github.com/nodejs/node-gyp/releases/tag/v10.2.0 🌻

@lukekarrys
Copy link
Member

@legendecas Thank you for merging and publishing this release! I wasn't aware that nodejs-foundation was setup to publish this package. Was publishing run automatically or as a manual step? I did some of the previous releases from my personal lukekarrys npm user but would much prefer to use the nodejs-foundation user if possible.

@legendecas
Copy link
Member

legendecas commented Jul 19, 2024

@lukekarrys it was published manually. I setup a automation at #3051 with nodejs-foundation user.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants